Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Using dynamic TreeViews

Note the following guidelines when using dynamic TreeViews, especially when upgrading from previous versions:

The optimized dynamic TreeView released as of Version 2.1A eliminates some private and undocumented APIs that are no longer used, but were present in previous versions of the dynamic TreeView.
If code in previous versions relies on the dynamic TreeView to be the source container of an object, you must review the logic, because for the optimized TreeView, the object’s source container is the dynamic frame, and the dynamic frame’s source container is the dynamic TreeView.
When configuring the number of frames to keep alive, you must ensure that the client machine running the given session can handle the maximum number of hidden frames because use of memory increases with an increasing number of running objects.
If you use node batching and also have the AutoSort attribute set to YES for the TreeView object (intending to sort the nodes), you must ensure that your data source (SDO) is sorting on the same fields specified as the fields to be displayed as the node label. This is required because when you use node batching, Dynamics ignores the AutoSort setting in order to ensure that ...More is always positioned as the last node in the TreeView. Otherwise, if the batched data does not come properly sorted from your data source, it will not be sorted in the TreeView. If you later turn off node batching (set RowsToBatch to 0 (zero)), the TreeView again functions according to the AutoSort setting.